dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProgramming of Applications dl-breadcrumb-item__separatorRuntime systems, OPC UA serverdl-breadcrumb-item__separatorData Link with Data Sources dl-breadcrumb-item__separatorData transmission
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Data transmission dl-permalink__symbolPermalink

At runtime of the local application, the data source variables that appear in the data source editor of the “Variables” tab are updated in configurable time intervals. The remote application is also executed at this time. Variables that are configured in the visualization, in the trend, as alarms, or for recipes are transferred and stored automatically. When a variable is accessed in IEC code only, the variable is not updated automatically. In this case, you need to select the “Update always” option in the data source editor of the “Variables” tab.

The data source types support the (read or write) data access to variables of the source PLC for the following data types:

  • Scalar value at top level

    Example: ‎PLC_PRG.hugo‎

  • Property to a program or GVL by means of a call when it is marked with ‎{attribute monitoring := 'call'}‎.

    Example: ‎PLC_PRG.PropertyCall‎

  • Variable which is mapped to bit addresses

    Example in ‎PLC_PRG‎: ‎x AT %MX0.5 : BOOL;‎

  • Variable (type ‎BIT‎) in a function block

    Example: Declaration in ‎DUT‎: ‎x, y : BIT‎, bit access: ‎PLC_PRG.dutInst.y‎

  • Structured obtainable variable

    Example: ‎PLC_PRG.outerInst.innerInst.dwVar‎

  • Property to POU instance when it is marked with ‎{attribute monitoring := 'call'}‎

    Example: ‎PLC_PRG.instance.PropertyCall‎

  • Property at top level and to an instance when it is marked with ‎{attribute monitoring := 'variable'}‎

    Note: This cannot be written by monitoring or by the data sources.

  • Array access with literal index

    Example: ‎PLC_PRG.arrOfInts[3]‎, ‎PLC_PRG.inst.arrOfBool[1]‎

  • Nested access (for example, array of structures or structure of arrays)

CAUTION

CAUTION
CAUTION
CAUTION

CAUTION

CAUTION

Bit access used in visualizations that are transferred via a data source connection function only if they contain literal offset specifications. A visualization cannot process an offset specification by defined constants.